Capacity sharing between wireless systems

ABSTRACT

One wireless telecommunications system includes a Mobile Central Office (MCO) for capacity sharing via a master scheduling system. The MCO is communicatively coupled to a plurality of wireless base stations, each being operable to handle a session from a wireless device and to handoff the session to another wireless base station when the wireless device moves into a range of the other base station. Each of the wireless base stations is operable to convey capacity information to the master scheduling system through the MCO, and to acquire capacity from one or more wireless base stations of another MCO when directed by the master scheduling system.

CROSS REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of U.S. patent applicationSer. No. 14/267,273, filed May 1, 2014, which application claimspriority to, and thus the benefit of an earlier filing date from, U.S.Provisional Patent Application No. 61/839,452, filed Jun. 26, 2013, theentire contents of which are hereby incorporated by reference.

BACKGROUND

Cellular telephony continues to evolve at a rapid pace. Cellulartelephone networks currently exist in a variety of forms and operateusing a variety of modulations, signaling techniques, and protocols,such as those found in 3G and LTE networks (3rd Generation of mobiletelecommunications technology and Long Term Evolution, respectively). Asconsumers require more capacity, the networks usually evolve. Forexample, some carriers, or Mobile Network Operators (MNOs), employ acombination of 3G and the faster LTE because, as demand for data andvoice increased, the MNOs needed faster networks. But, a completeoverhaul of the MNOs entire network from 3G to the faster LTE would notbe practical or economical. And, the MNOs need to operate both networksuntil the slower network is eventually phased out.

And, the very different ways in which the networks operate furthercomplicate network changes. For example, 3G networks would handlewireless communications through a base station by connecting thecommunications to a Public Switching Telephone Network (PSTN) through aMobile Telephone Switching Office (MTSO) of the MNO. In LTE, however,wireless communications through base stations are typically handledthrough packet switching networks so a connection to the PSTN is notnecessary in many cases. In either case, each network of a MNO includessome sort of Mobile Central Office that is operable to handle thecommunications between wireless devices (also known as user equipment)and base stations.

Still, even with these faster networks, the demand for more data appearsto outpace MNO capabilities. And, the demand can change from day to dayor even hour to hour. For example, when a location experiences a rapidincrease in population, such as what occurs during sporting events, theMNOs capacity can be overwhelmed. And, when an MNO's capacity isoverwhelmed, communications between user equipment and base stations getdropped.

SUMMARY

Systems and methods presented herein provide for capacity sharingbetween wireless systems via a master scheduling system. In oneembodiment, a wireless telecommunications system includes a plurality ofwireless base stations and a Mobile Central Office (MCO) communicativelycoupled to each of the wireless base stations. Each wireless basestation is operable to handle a session (i.e., a voice call, a dataconnection, a Voice Over Internet Protocol, etc.) from a wireless device(also known as user equipment) and to handoff the session to another ofthe wireless base stations when the wireless device moves into a rangeof the other wireless base station. Each of the wireless base stationsis operable to convey capacity information to the master schedulingsystem through the MCO, and to acquire capacity from one or morewireless base stations of another MCO when directed by the masterscheduling system.

The various embodiments disclosed herein may be implemented in a varietyof ways as a matter of design choice. For example, some embodimentsherein are implemented in hardware whereas other embodiments may includeprocesses that are operable to implement and/or operate the hardware.Other exemplary embodiments, including software and firmware, aredescribed below.

BRIEF DESCRIPTION OF THE FIGURES

Some embodiments of the present invention are now described, by way ofexample only, and with reference to the accompanying drawings. The samereference number represents the same element or the same type of elementon all drawings.

FIG. 1 is a block diagram of an exemplary wireless telecommunicationssystem.

FIG. 2 is a flowchart illustrating an exemplary process of a wirelesstelecommunications system.

FIGS. 3A and 3B illustrate exemplary interactions between user equipmentand base stations.

FIGS. 4A-4C illustrate exemplary interactions between user equipment andbase stations configured with WiFi.

FIGS. 5-8 illustrate embodiments in which the MCOs coordinate to requestcapacity for subscribers.

FIGS. 9-23 illustrate exemplary signaling techniques in which capacityamong MCOs can be shared dynamically.

FIG. 24 is a block diagram of an exemplary computing system in which acomputer readable medium provides instructions for performing methodsherein.

DETAILED DESCRIPTION OF THE FIGURES

The figures and the following description illustrate specific exemplaryembodiments of the invention. It will thus be appreciated that thoseskilled in the art will be able to devise various arrangements that,although not explicitly described or shown herein, embody the principlesof the invention and are included within the scope of the invention.Furthermore, any examples described herein are intended to aid inunderstanding the principles of the invention and are to be construed asbeing without limitation to such specifically recited examples andconditions. As a result, the invention is not limited to the specificembodiments or examples described below.

FIG. 1 is a block diagram of an exemplary wireless telecommunicationssystem. In this embodiment, the system includes a first MCO 101 that isoperable to handle communications between a set 103 of base stations 106and user equipment operating within the range of the base stations 106.For example, the MCO 101 may be operated by a first mobiletelecommunications carrier, or MNO. The set 103 may represent aparticular market/geographical region in which the telecommunicationscarrier operates. Each base station is operable to cover a “cell” 110 ofthat geographical region. A wireless device (not shown), such as amobile handset or other user equipment, may be in communication with afirst of the base stations 106 and move to another location such thatthe wireless device is now in communication with a second of the basestations 106. The MCO 101 is operable to manage the communication of thewireless device from the first base station to the second base station.A second MCO 102 may operate in similar fashion with a set 104 of basestations 106. Alternatively, the MCO 102 may simply represent a wirelessnetwork or wireless entity. In any case, the MCO 102 represents anentity that is separate and distinct from the MCO 101.

Examples of the MCOs 101 and 102 include Mobile Telephone SwitchingOffice (MTSOs) for mobile routing of data sessions and/or voice calls.An MTSO contains switching equipment for routing mobile phone calls fromuser equipment through the base stations. The MTSO interconnects callsfrom the user equipment with the landline telephone companies and otherwireless carriers by connecting the calls to the Public SwitchedTelephone Network (PSTN). In many instances, the MTSO also conveys datafrom between user equipment and the internet via an over-the-airinterface of the base stations and a connection to an internet backbone.The MTSO also provides resources needed to serve a mobile subscriber,such as registration, authentication, location updating and callrouting. The MTSO may also compile billing information for subscribersvia back office systems.

Other examples of the MCOs include packet switching, such as that foundin LTE. In this case, data session services are provided to mobiledevices. An IP Multimedia Core Network Subsystem (IMS) can also be usedin LTE networks to couple user equipment to internet connections so asto convey both data and voice over the Internet, including Voice OverInternet Protocol (VOIP). Generally, though, LTE networks have equipmentat base stations 106 that couple directly to the Internet. Thus, MCOs asused herein may represent such equipment.

Based on the forgoing, an MCO is any system, apparatus, software, orcombination thereof operable to maintain or otherwise support wirelesscommunications, including data and voice, with subscribers via userequipment (e.g., mobile handsets and other wireless devices).Accordingly, the MCO may be a wireless communications carrier or networkemploying, for example, 2G, 3G, LTE, WiFi, or any combination thereof.And, a base station 106 is any device or system operable to communicatewith user equipment via Radio Frequency (RF).

As mentioned, the MCO 101 may be controlled and operated by a firstmobile telecommunications carrier, or MNO. The second MCO 102, in thisembodiment, is controlled and operated by a second telecommunicationscarrier or some other wireless network. In some instances,telecommunications carriers share antenna towers and/or have cells 110that overlap within each other's geographic regions. An example of suchis illustrated in the region 105 where the sets 103 and 104 intersect.For example, the base stations 106 within the region 105 may representantenna towers that comprise antennas belonging to the MCO 101 and theMCO 102. Alternatively or additionally, the cells 110 within the region105 may represent overlapping cells associated with the base stations106. That is, a cell 110 within the region 105 may comprise a basestation 106 belonging to the MCO 101 and a base station 106 belonging tothe MCO 102.

In any case, an MCO may occasionally experience a need for increasedcapacity. For example, each base station 106 may be capable of handlingcommunications for a certain number of users via their respectivedevices (i.e., user equipment). When a base station 106 is at itsmaximum capacity and another user initiates or continues a session withthat base station 106, that breach of capacity can cause sessions to bedropped. At the very least, the maximum capacity prevents the other userfrom having a session with that base station 106 and the MCO. Toovercome such problems, the MCO 101 is configured to request capacityfrom another wireless telecommunication system, such as the MCO 102.

Generally, when MCOs are owned, managed, or otherwise controlled byseparate entities, the competitive nature of the environment preventscooperation among the MCOs 101 and 102. However, the ability to sharecapacity among the MCOs 101 at 102 can be quite beneficial. For example,in emergency situations where one MCO happens to be over capacity withits subscribers and the other MCO operating in the same area is not,moving capacity from the other MCO would allow the over capacity MCO toestablish communications for more of its subscribers and ensure thatcalls go. And, there are certainly commercial advantages to sharingcapacity. For example, if capacity is not being used by one MCO, thenthat capacity could be offered to another MCO for commercial benefit.

As used herein, capacity may include RF spectrum, data throughput,backhaul capacity, network processing (e.g., virtualized Radio AreaNetworks, or “RANs”, also known as Cloud RANs), channels in a TimeDivision Multiple Access (TDMA) signal, Code Division Multiple Access(CDMA) channels, channels in a Frequency Division Multiple Access (FDMA)signal, channels in the Orthogonal Frequency Division Multiplexing(OFMD), Carrier Sense Multiple Access (CSMA), and the like. Backhaulcapacity may include, among other things, a backhaul portion of anetwork including intermediate links between a core network (or abackbone network) and smaller subnetworks at an edge of a hierarchicalnetwork. Backhaul capacity can also include an obligation to carry datapackets to and from a global network, and the like.

To implement the capacity sharing concepts in this embodiment, the basestations 106 of the MCOs 101 and 102 are operable to communicatecapacity information through their respective MCOs to a master scheduler175 such that the master scheduler can request capacity from otherwireless telecommunication systems. For example, the master scheduler175 may monitor the capacity of the base stations 106 of each of theMCOs 101 and 102. When the master scheduler 175 detects that capacitymay be exceeded by a base station 106 of the MCO 101, the masterscheduler 175 may acquire excess capacity from a base station 106 of theMCO 102. In this regard, the master scheduler 175 may direct the basestation 106 of the MCO 102 to relinquish that excess capacity and directthe base station 106 of the MCO 101 to acquire that excess capacity (orsome other amount of capacity) to alleviate the need. After the need foradditional capacity subsides, the base station 106 of the MCO 101 mayrelinquish the capacity to the master scheduler 175 through the MCO 101such that the other base station 106 may reacquire it.

As used herein, the master scheduler 175 is any system, device,software, or combination thereof operable to interface and communicatewith a plurality of MCOs to coordinate/manage capacity sharing among theMCOs. In this regard, the master scheduler 175 may be operable tointerface using any of a variety of protocols and/or communicationtechniques available to the MCOs from which it requests capacity.

FIG. 2 is a flowchart illustrating an exemplary process 200 of awireless telecommunications system. In this embodiment, a link isestablished from a first wireless base station 106 to the masterscheduler 175 through its respective MCO, in the process element 201.For example, communication links between the base stations 106 of theMCO 101 may be established through the MCO 101 to the master scheduler175. From there, the master scheduler 175 can monitor the capacity oneach of the base stations 106 of the MCO 101. In this regard, the firstbase station 106 of the MCO 101 conveys capacity information to themaster scheduler 175 through the MCO 101, in the process element 202.

When the master scheduler 175 detects a capacity issue on the first basestation 106 of the MCO 101, the master scheduler 175 may acquireadditional capacity from other wireless telecommunication systemsincluding one or more the base stations 106 of the MCO 102. Onceacquired, the master scheduler 175 directs the first wireless basestation 106 to acquire the capacity, in the process element 203.

To illustrate, the base station 106-1 may have an antenna mounted on atower and operable to handle communications from user equipmentoperating within the cell 110-1. When the base station 106-1 encountersanother session with other user equipment that exceeds the capability ofthe base station 106-1, the master scheduler 175 detects the exceededcapability and requests capacity from a base station 106 of the MCO 102.The master scheduler 175 then directs the base station 106-1 to beginusing the acquired capacity. Once finished, the base station 106-1relinquishes the capacity to the master scheduler 175 such that the basestation 106 of the MCO 102 can reacquire that capacity.

Again, to request and relinquish capacity, the master scheduler 175 maybe configured to operate in a variety of communication protocols. Forexample, the MCO 101 may communicate to its base stations 106 via aparticular protocol that differs from the protocol in which the MCO 102communicates with its wireless base stations 106. Accordingly, themaster scheduler 175 may be operable to communicate with each of theirMCOs 101 and 102 via the respective communication protocols. Somenon-limiting examples of various manners in which the user equipment maycommunicate through the acquired capacity are now shown in FIGS. 3A, 3B,and 4A-4C.

Example

FIGS. 3A and 3B illustrate exemplary interactions between user equipment125 and base stations 106. More specifically, FIGS. 3A and 3B illustratetwo separate base stations 106-101 and 106-102 sharing the same antennatower. The base station 106-101 is controlled by the MCO 101 and thebase station 106-102 is controlled by the MCO 102. In FIG. 3A, the basestation 106-101 has established a session and is communicating with theuser equipment 125-1 and is currently at capacity. Another userequipment 125-2 then attempts to establish a session with the basestation 106-101. The MCO 101 detects this situation and communicateswith the MCO 102 to request an amount of excess capacity that the MCO102 may have.

As can be seen in FIG. 3A, the base station 106-102 has a sessionestablished with the user equipment 125-3. However, the base station106-102 still has capacity available for use by the base station106-101. Thus, the base station 106-101, after requesting the excesscapacity from the MCO 102, acquires the excess capacity by directing theuser equipment 125-2 to establish a session with the base station106-102, as illustrated in FIG. 3B.

Alternatively, the MCO 101, after negotiating with the MCO 102 forcapacity, may simply acquire the capacity in the form of a frequencyband that is allocated to the MCO 102. For example, the MCO 102 may havea license to a particular frequency band that differs from that of theMCO 101 so they won't interfere with one another on the same antennatower. After the MCO 101 negotiates with the MCO 102 for additionalcapacity, the MCO 102 may simply relinquish that capacity and preclude,at least temporarily, its subscribers from using that frequency band.Thereafter, the MCO 101 may direct its subscribers to use the frequencyband acquired from the MCO 102 by transmitting control messages to theuser equipment of the subscribers that direct the user equipment tochange frequency bands.

As discussed above, the capacity to be acquired may be any of a numberof different types of communication technologies. For example, theacquired capacity may be a channel of the communication technologyimplemented by the MCO 102 through the base station 106-102. Thus, ifthe user equipment 125-2 is compatible, either the MCO 101 or the MCO102 directs the user equipment 125-2 to establish a session with thebase station 106-102. This may entail the user equipment 125-2 occupyinga CDMA channel, an FDMA channel, a TDMA channel, an OFDM channel, etc.on the base station 106-102 depending on the communication technologybeing implemented on the base station 106-102.

Example

FIGS. 4A-4C illustrate exemplary interactions between user equipment 125and base 106 stations configured with WiFi. In this embodiment, the basestations 106-101 and 106-102 are still configured on the same antennatower. The base stations 106-101 and 106-102 are also configured withWiFi access points 130 that provide Internet access to the userequipment 125. Thus, the user equipment 125-1 and 125-2, beingsubscribers to the MCO 101, are operable to communicate data and/orvoice via the WiFi access points 130-101 associated with the basestation 106-101 and the MCO 101. Similarly, the user equipment 125-3 isoperable to communicate data and/or voice via the WiFi access point130-102 associated with the base station 106-102 and the MCO 102.

In FIG. 4A, the user equipment 125-2 is attempting to establish asession with the base station 106-101 by way of either of the WiFiaccess point 130-101 or through the cellular communications beingemployed by the base station 106-101. However, as the user equipment125-2 attempts to establish a session with the base station 106-101and/or the WiFi access point 130-101 (collectively the MCO 101), it iseither being blocked by the signal from the WiFi access point 130-102 orthe capacity for the base station 106-101 has reached its capacity.Thus, the MCO 101 may request additional capacity from the MCO 102 suchthat the user equipment 125-2 can establish a session.

In FIG. 4B, the capacity is acquired by a negotiation between the MCO101 and the MCO 102 to direct the MCO 102 to decrease the signalstrength of the WiFi access point 130-102 and/or change the direction ofthe WiFi signal. Thus, the user equipment 125-2 can establish a sessionwith the MCO 101. Alternatively, as shown in FIG. 4C, the negotiationbetween the MCO 101 and the MCO 102 results in directing the user 125-2to establish a session with the MCO 102 (e.g., via the WiFi access point130-102 and/or the base station 106-102). Accordingly, those skilled inthe art will readily recognize that the invention is not intended to belimited to any form of capacity sharing. And, it should be noted thatthe capacity may be dynamically shared among MCOs. For example, the MCOsvia their local schedulers or other scheduling systems may automaticallyexchange capacity with one another based on need. Thus, if one MCO needscapacity, its scheduling system may automatically retrieve that capacityfrom another MCO (i.e., assuming it is a cooperative MCO) for as long asthe capacity is needed or until the other MCO requires the capacity.

FIGS. 5-8 illustrate embodiments in which the MCOs coordinate to requestcapacity for subscribers. More specifically, FIG. 5 illustrates an MCO101 with a local scheduler 155 operable to request additional capacityfrom other MCOs 102-103. FIG. 6 illustrates an exemplary coordination ofcapacity requests from an MCO 101 using satellites 160, such as GPSsatellites, to provide timing for the capacity requests. FIG. 7illustrates an exemplary master scheduler 175 that is operable tocoordinate capacity requests with local schedulers 155 of MCOs 101-103and to request capacity on their behalf. FIG. 8 illustrates an exemplarymaster scheduler 175 that is operable to detect capacity issues amongMCOs 101-103 and request capacity on their behalf.

In FIG. 5, the MCO 101 is configured with a local scheduler 155 that isoperable to detect capacities of its base stations 106. The MCOs 102 and103 may be configured with similar local schedulers 155 that areoperable to detect the capacities of their base stations 106. Forexample, each MCO may be configured with a plurality of base stations106 to provide wireless services to its subscribers. In this regard,each MCO be associated with a different operating entity as discussedabove. And, each scheduler 155 of the MCOs is operable to detectcapacity of its various base stations 106 so as to request additionalcapacity from other MCOs when needed. Thus, a scheduler 155 is anysystem, device, software, or combination thereof operable to detectcapacities of base stations 106 within its operating zone and requestcapacity from other MCOs and/or other wireless providers.

To illustrate, the scheduler 105 of the MCO 101 continually detectscapacity of the base stations 106-1-106-N operating within its zoneindicated by the dashed line (where the reference “N” is merely intendedto indicate an integer greater than “1” and not necessarily equal to anyother “N” reference herein). The local scheduler 155 of the MCO 101 thendetects a capacity issue with the base station 106-1 and forms capacityrequests for the MCO 102 and the MCO 103.

The MCOs 102 and 103, via their local schedulers 155, may alsocontinually detect capacity issues with their base stations 106.Accordingly, when the local scheduler 155 of the MCO 102 receives arequest from the MCO 101, the local scheduler 155 determines if it hasany capacity available to share with the MCO 101. In this embodiment,the local scheduler 155 of the MCO 102 detects that capacity isavailable on the base station 106-N and directs that base station torelease its capacity (e.g., by only allowing a lesser number ofsubscribers to access the base station 106-N). The base station 106-N ofthe MCO 102 then releases its capacity to the local scheduler 155 of theMCO 102 such that the local scheduler 155 of the MCO 102 can grant thecapacity to the local scheduler 155 of the MCO 101. Once that capacityis granted, the subscribers on the base station 106-1 can begin usingthat capacity (e.g., in one or more of the manners describedhereinabove).

As capacity can be granted, it can also be denied. In this embodiment,the local scheduler 155 of the MCO 103 also receives a request from thelocal scheduler 105 of the MCO 101 for additional capacity. The localscheduler 105 of the MCO 103 determines that it has no availablecapacity and denies the request to the local scheduler 155 of the MCO101. Alternatively, a denial of requested capacity may be the result ofMCOs being expressly from cooperating with one another (e.g.,contractually precluded).

It should be noted that the invention is not intended to be limited toany particular amount of available capacity being requested. Rather, alocal scheduler 155 may be able to request capacity for any number ofsubscribers. For example, the local scheduler 155 of the MCO 101 mayneed additional capacity for a single subscriber. Accordingly, the localscheduler 155 of the MCO 101 may request capacity from each of the MCOs102 and 103 for that subscriber. Additionally, capacity requests may bebased on prioritization. For example, a priority subscriber, such as anemergency response person, may be a subscriber to only the MCO 101.However, to ensure that the priority subscriber has access tocommunications as needed, the user equipment of the priority subscribermay be operable to direct the local schedulers 155 to coordinate toensure that the priority subscriber has wireless access as desired.

It should also be noted that the invention is not intended to be limitedto capacity requests being made only for subscribers of individual MCOs.For example, FIG. 5 illustrates another wireless provider 150 beingcommunicatively coupled to the MCO 101. In this embodiment, the wirelessprovider 150 provides wireless services to a separate set of wirelesssubscribers. However, in certain geographical regions, that wirelessprovider 150 may use (e.g., lease) capacity from the MCO 101.Accordingly, the local scheduler 155 may be operable to requestadditional capacity for subscribers of the wireless provider 150communicating within the operating zone of the MCO 101.

The capacity requests can be implemented in a variety of ways as amatter of design choice. For example, the local schedulers 155 of theMCOs 101-103 may be linked through an Internet connection with softwarethat communicates between the MCOs to negotiate and share capacity. Inthis regard, one or more the MCOs 101-103 may have cellular transceiversconfigured with their respective base stations 106 so as to communicatedirectly through the Internet. Examples of such include LTEtransceivers, such as eNodeB. In other embodiments, the local schedulers105 of the MCOs 101-103 may communicate through a common communicationlink and common communication protocol to negotiate capacity sharing.This communications link may be carried over wireless channels betweenthe separate wireless systems. Accordingly, the invention is notintended be limited to any manner in which the MCOs 101-103 negotiateand share capacity. An example of one embodiment of a communication linkbetween the local schedulers 155 is illustrated FIG. 6.

In FIG. 6, the local schedulers 125 of the MCOs 101 and 102 communicatewith one another through a communication link 161 to share capacity withone another, including backhaul capacity described above. For example,when the local scheduler 105 of the MCO 101 requests capacity from thelocal scheduler 105 of the MCO 102, the local scheduler 155 of the MCO102 may grant the capacity through the communication link. Such may alsoentail allowing the subscriber of the MCO 101 to communicate on the basestations 106 of the MCO 102 (via data and/or voice) and then transferthat communication to the MCO 101 over the communication link such thatthe back office systems of the MCO 101 can associate the billing andother information with the subscriber.

Also, cellular data sessions or telephony generally require timingsignals to coordinate communications and communication handoffs amongbase stations 106. Thus, when one subscriber is operating under theshared capacity of another MCO, timing information to manage thecommunications may be passed over the communication link 161 between thelocal schedulers 155 of the MCOs 101 and 102. One example of theprotocol used for such timing includes the IEEE 1588 timing protocol.Alternatively or additionally, the local schedulers 105 of the MCOs 101and 102 may receive timing information from satellites 160. For example,GPS satellites transmit timing and location information for receiversbelow. The MCOs 101 and 102 may use this timing information tocoordinate their requests, call handling, and/or capacity sharing.

Again, the communication link 161 is not intended to be limited to anyparticular form. For example, the communication link 161 may be an“air-to-air” interface between local schedulers 155 of the MCOs 101 and102. Alternatively or additionally, the communication link 161 may be alandline, an Internet connection, or the like. And, this embodiment(including the use of timing via the satellites 160) may be combinedwith other embodiments disclosed herein.

In FIG. 7, an exemplary master scheduler 175 is operable to coordinatethe capacity requests with local schedulers 155 of MCOs 101-103. Themaster scheduler 175 is communicatively coupled to each of the MCOs101-103 to coordinate the capacity sharing requests via their respectivelocal schedulers 155. In this regard, the local schedulers 155 of theMCOs 101-103 are operable to detect the capacity of their respectivebase stations 106 to determine if and when additional capacity should berequested.

To again illustrate with the MCO 101, the local scheduler 155 of the MCO101 detects a capacity issue with one of its base stations, the basestation 106-1. Accordingly, the local scheduler 155 formats a requestfor additional capacity and transfers the request to the masterscheduler 175. The master scheduler 175 then conveys the request forcapacity to the local schedulers 155 of the MCOs 102 and 103. Such maybe done in the event that the MCOs operate under unique communicationsprotocols that may be incompatible with one another.

The local schedulers 155 of the MCOs 102 and 103, as they arecontinually detecting the capacity of the respective base stations 106,then make a determination if they have any available capacity to share.In this embodiment, the local scheduler 155 of the MCO 102 determinesthat capacity is available from one of its base stations 106-1. Thelocal scheduler 155 of the MCO 102 then directs the base station 106-1to release its capacity (e.g., limit the number of subscribers accessingthe base station 106-1). The local scheduler 155 of the MCO 102 thenindicates to the master scheduler 175 that the capacity has beenreleased.

Once the capacity has been released to the master scheduler 175, themaster scheduler 175 indicates such to the local scheduler 155 of theMCO 101 such that the MCO 101 may direct its subscribers to begin usingthe added capacity. The local scheduler 155 of the MCO 101, in thisregard, maintains control of the requesting capacity until it is nolonger needed by the base station 106-1. Once that capacity is no longerneeded, the base station 106-1 releases the capacity such that the localscheduler 155 of the MCO 101 can indicate such to the master scheduler175. The local scheduler 155 of the MCO 102, when notified by the masterscheduler 175, then reacquires the capacity for base station 106-1.

Again, just as the capacity can be released and shared, it can also bedenied. In this regard, the master scheduler 175 issues a capacityrequest to the local scheduler 155 of the MCO 103. The local scheduler155 of the MCO 103 determines that it has no capacity available anddenies the request to the master scheduler 175.

FIG. 8 illustrates another exemplary master scheduler 175 that isoperable to detect capacity issues among MCOs 101-103 and requestcapacity on their behalf. In this embodiment, the master scheduler 175is operable to detect capacity issues on behalf of the MCOs 101-103,thereby essentially eliminating the need for the local schedulers 155 tomanage capacity. In other words, the master scheduler 175 in thisembodiment offloads the local scheduler duties of the MCOs 101-103.

As the master scheduler 175 is operable to detect capacities of the basestations 106-1-106-N of each of the MCOs 101-103, the master scheduler175 is operable to determine when a base station 106 can use morecapacity. Again using the base station 106-1 of the MCO 101, the masterscheduler 175 determines a capacity issue with the base station 106-1and issues a capacity requests to the base stations with availablecapacity. To illustrate, the master scheduler 175 requests capacity fromthe base station 106-N of the MCO 102 and from the base station 106-1 ofthe MCO 103.

As the master scheduler 175 makes a determination whether capacity isavailable or not, there is no need for a base station 106 or, for thatmatter, an MCO to deny a capacity request. In other words, the masterscheduler 175 detects and manages the capacities of the base stations106 on behalf of the MCOs 101-103. Accordingly, when the masterscheduler 175 issues the capacity request to the base station 106-N ofthe MCO 102 and to the base station 106-1 of the MCO 103, that capacityis released to the master scheduler 175. The master scheduler 175, inturn, grants the capacity to the base station 106-1 of the MCO 101 suchthat the MCO 101 can direct its subscribers to use the acquiredcapacity. When the capacity is no longer needed, the base station 106-1releases the capacity to the master scheduler 175 which, in turn,returns the capacity to the base station 106-N of the MCO 102 and to thebase station 106-1 of the MCO 103.

FIGS. 9-23 illustrate exemplary signaling techniques in which capacityamong MCOs can be shared, be it through FDMA, CDMA, TDMA, OFDM, packetswitching, or the like. Cellular communication systems generallytransmit in both directions simultaneously (i.e., duplexcommunications), be it data or voice. Thus, it is also generallynecessary to be able to specify the different directions of transmissionin the signaling. The uplink side (UL) of the duplex communicationsincludes transmissions from the user equipment to the eNodeB or basestation 106. And, the downlink side (DL) of the duplex communicationsincludes transmissions from the eNodeB or base station 106 to the userequipment. As used herein, eNodeBs are any systems, devices, software,or combinations thereof operable to communicate with user equipment viabase stations 106.

The following FIGS. 9-23 illustrate the UL and DL sides of signaltransmissions with the frequency domain being represented vertically andthe time domain being represented horizontally, in accordance withexemplary embodiments of the invention. More specifically, FIGS. 9-13illustrate various exemplary Time Division Duplex (TDD) LTE signalingtechniques, FIGS. 14-18 illustrate various exemplary Frequency DivisionDuplex (FDD) LTE signaling techniques, and FIGS. 19-23 illustratevarious exemplary shared eNodeB LTE signaling techniques, each of whichmay be implemented, either alone or in combination, with the capacitysharing embodiments described above. And, in the following embodimentsof the FIGS. 9-23, certain elements have the same or similar meanings.For example, the element 301 throughout the drawings indicates aPhysical Downlink Control Channel (PDCCH) whereas the element 302indicates a Downlink Shared Channel (DL-SCH). The PDCCH 301 carriesdownlink allocation information and uplink allocation grants for aterminal. And, the DL-SCH 302 carries synchronization signals PSS andSSS for the user equipment to discover an LTE cell.

In LTE, the DL-SCH elements 302 are generally configured at the centerof the channel and a Master Information Block (MIB) is transmittedtherefrom. For example, in order to communicate with a network, the userequipment obtains basic system information, which is carried by the MIB(static) and a System Information Block (dynamic; “SIB”). The MIBcarries the system information including system bandwidth, System FrameNumber (SFN), and a Physical Hybrid Automatic Repeat Request (PHARM)Indicator Channel Configuration, or PHICH.

The MIB is carried on a Broadcast Channel (BCH) and mapped into aPhysical Broadcast Channel (PBCH), which is transmitted with a fixedcoding and modulation scheme that can be decoded after an initial cellsearch procedure. With the information obtained from the MIB, userequipment can decode a Control Format Indicator (CFI), which indicatesthe PDCCH length and allows the PDCCH 301 to be decoded. The presence inthe PDCCH 301 of a Downlink Control Information (DCI) message scrambledwith System Information Radio Network Temporary Identifier (SI-RNTI)indicates that an SIB is carried in the same subframe.

The SIB is transmitted in the Broadcast Control Channel (BCCH) logicalchannel and BCCH messages are generally carried and transmitted on theDL-SCH 302. Control signaling is used to support the transmission of theDL-SCH 302. Control information for user equipment is generallycontained in a DCI message transmitted through the PDCCH 301. The numberof MNOs (again, “Mobile Network Operators”), the allocation percentageper MNO, and the expected variation in allocation generally determineoptimal locations for the center of each DL-SCH 302, thereby limitingthe probability of DL-SCH 302 relocations.

When employing TDD in an LTE network, time coordination is used betweenthe eNodeBs in the LTE network, including coarse time coordination, finetime coordination, and synchronized time coordination. Coarse timecoordination means that at least two eNodeBs share a clock withresolution greater than a clock pulse. Fine time coordination indicatesthat at least two eNodeBs share a clock with resolution less than thelength of a cyclic prefix. Synchronized time coordination means thatsample clocks are locked between the two eNodeBs. Again, these timingconsiderations may be implemented in a variety of ways as a matter ofdesign choice. For example, eNodeBs may receive their clock signals fromlocal schedulers 155, master schedulers 175, satellites 160, networkclocks, or the like.

When employing FDD in an LTE network, frequency coordination is used tobetween the eNodeBs in the LTE network. Generally, frequencycoordination and allocation is semi-static, real time, and/or dynamic.Semi-static spectrum allocation means that spectrum allocation isprovisioned by MNO agreements and changes infrequently. Real-timespectrum allocation means that spectrum allocation between MNOs that canvary dynamically based on resource needs and scheduler capability (e.g.,the schedulers 155 and 175). Allocations are flexible within bounds thatare configured by agreement between MNOs. Dynamic scheduling meanschannel time allocations that are variably sized for each MNO.

Other features common throughout FIGS. 9-23 include guard times 320 thatare relevant to the timing considerations just mentioned and guard bands330 that are relevant to the frequency considerations just mentioned.Also in FIGS. 9-23 are first downlink channels represented by thereferences DL M1 303, second downlink channels represented by thereferences DL M2 304, first uplink channels represented by thereferences UL M1 305, and second uplink channels represented by thereferences UL M2 306.

Generally, in LTE DLs, two synchronization signals are transmitted insix center Resource Blocks (RBs), including a Primary Sync Signal (PSS)and a Secondary Synchronization Signal (SSS). Information about systembandwidth is contained in the MIB and is expressed as some number of kHzabove or below the center frequency. When a UE initially comes online,it finds the PSS/SSS and then the MIB.

When operators (e.g., MNOs/MCOs) share spectrum, the variability of thespectrum sharing can vary dynamically based on factors of 10milliseconds or a number of times in an LTE frame. Since PSS, SSS, MIB,and SIB s are transmitted at the center of the spectrum, dynamicallyvarying the spectrum sharing between two operators means that thesesynchronization and system messages are frequently re-aligned.Accordingly, with the embodiments disclosed herein, the center frequencyblock of each of the operators can be changed on a slower changingtimeline compared to the variability of the spectrum sharing. Once userequipment locks onto the LTE system, it is up to the eNodeB to allocateRBs to each user equipment. Although dynamically changing the spectrumsharing generally means changing the system bandwidth and that thesynchronization and system information messages are no longertransmitted in the “true center” of the new system bandwidth, an eNodeBof a first operator can simply not allocate the portion of the RBs thatno longer belong to that operator as that portion is now taken up byanother operator.

This mode of operations can persist until the eNodeB deems that a changeof center frequency is either necessary or convenient to do so withoutdisrupting the user equipment attached to the LTE system. An example ofsuch includes when system bandwidth has changed (e.g., reduced or moved)so much that it resulted in the synchronization and system informationmessages needing to be sent outside of the system bandwidth. Anotherexample might include when user equipment is not actively receivingtraffic on a DL or sending traffic on a UL.

A new messaging may be used to indicate the new position of the centerfrequency blocks to assist the user equipment in finding the new center.This message may be sent via the SIB, the MIB, and/or the PDCCH (e.g.,the DL control channel). In the PDCCH, seven new bits may be defined tosend the new center frequency. A 2-bit counter indicates a number offrames ahead in time when new center frequency adjustment takes place,with a “0” value of the counter indicating the current center frequency.

The amount of guard time 320 should be sufficiently long to ensure userequipment can lock onto the new center frequency. If two operators donot share eNodeBs, the eNodeBs need to communicate either OTA or via thebackbone. In other words, an inter-operator X2 interface can be defined.In the case where the eNodeBs from first and second operators operatemore on a master-slave basis, then one eNodeB could be configured to actas user equipment to another eNodeB, and thus be allocated resources toin turn reallocate the resources to the user equipment in its system.

With this in mind, the acquired capacity in the following embodimentscan be considered as an access to spectrum that is multiplexed in timeand/or frequency blocks. For example, for a first second, an MNO mayreceive a 10 Mhz block of bandwidth. For the next two seconds, that MNOmay receive a 20 Mhz block of bandwidth, and then the MNO reverts backto the 10 MHz of bandwidth for one second. Alternatively, the MNO mayreceive a 10 Mhz block of bandwidth indefinitely or even receive theblock periodically, one second of access followed by two seconds of noaccess, with the pattern repeating. FIGS. 9-23 illustrate variouscombinations of these concepts. And, once an MNO acquires the capacity,it can place its own TDMA, CDMA and/or OFDMA channels/signals within thecapacity block allocations.

Turning now to the TDD LTE signaling techniques of FIGS. 9-13 in whichcapacity sharing may be employed, FIG. 9 illustrates a TDD-LTE TDMsignaling with a non-shared eNodeB and static timing allocations. Inthis embodiment, the guard time 320-2 is generally longer than the guardtimes 320-1 and 320-3. The guard time 320-2 is also generally dependenton a round-trip delay of a signal between a base station 106 and userequipment.

In this embodiment, the channels DL M1 303, DL M2 304, UL M1 305, and ULM2 306 occupy the entire spectrum being allocated with the time domainallocation being static. This signaling technique employs predefinedtime allocations and leverages existing user equipment and eNodeBs withrelatively little change in transmission. The user equipment handles twodistinct PDCCHs 301 on the same band that are controlled by the MNO. Thestatic time domain allocation may be configured manually and thusrequires no new interfaces. Even though RF parameters and cellsize/layout may differ for each MNO, no inter-MNO interfaces needed.And, as the guard times 320 absorb clock differences, timingsynchronizations can be more loosely defined. This embodiment providesthe MNOs with the ability to have multiplexed access to a singlefrequency bandwidth channel in a synchronized manner based on resourcenegotiation.

In FIG. 10, a TDD-LTE TDM signaling technique is illustrated withnon-shared eNodeB and dynamic time allocation. The channels DL M1 303,DL M2 304, UL M1 305, and UL M2 306 in this embodiment again occupy theentire spectrum of the allocated frequency band but the time domainallocation is variable. The user equipment again handles two distinctPDCCHs 301 on the same band, which are controlled by the individualMNOs. Time allocation scheduling may be implemented with a customizedinter-MNO interface. And, the guard times 320 absorb clock differencesto provide for more loosely defined timing synchronizations. If WiFi isused to transmit (e.g., in the 2.4 GHz-2.5 GHz and the 5.7 GHz-5.9 GHzbands), the guard times 320 may be established via the DistributedCoordination Function (DCS) (i.e., via the DCF Interframe Space, or“DIFS” duration) of the IEEE 802.11 standards as follows: (guard time320)≥(DIFS)≤(time required for transmission of a larger packet of data).This allows an eNodeB to sniff WiFi signals and track the NAV field toefficiently reclaim a channel after WiFi transmissions. This embodimentalso provides the MNOs with the ability to employ a duty cycle ofperiodic multiplexed access that can be updated based on a currentnegotiated resource allocation negotiation across networks.

In FIG. 11, a TDD-LTE semi-static FDM signaling technique is illustratedwith non-shared eNodeB. In this embodiment, the frequency spectrum isdivided between two MNOs 331 and 332 in a static configuration (e.g.,MNO 331 and MNO 332 being analogous to MCO 101 and MCO 102). Each of theMNOs 331 and 332 operate their sub-bands independently with respect totheir RF parameters and scheduling/resource allocation within itsrespective sub-band. Generally this means that the M1 and M2 channelsnegotiate to adjust frequency spectrum splits. In this regard, thesplits are separated by frequency guard bands 330 such that the spectrumsplits can be more loosely defined.

In FIG. 12, a TDD-LTE semi-static time-coordinated FDM signalingtechnique is illustrated with non-shared eNodeB. Generally, timecoordinated means that, at any instant in time, both the M1 and M2channels are either UL or DL, and thus does not ensure orthogonality.Accordingly, eNodeBs are synchronized to ensure orthogonality. Thefrequency spectrum split of the M1 and M2 channels is semi-static butdoes not match for the UL and DL. The arrow 340 indicates that there isno shift of the PSS and SSS signals is needed if its current locationremains within the MNO allocation. This embodiment is similar to thatshown in FIG. 11, in that it generally employs time coordination so thatthe UL and DL can operate in the same time windows. This timecoordination may require inter-MNO interfaces for the MNOs 331 and 332.And, since this does not require time or frequency synchronization, thissignaling technique allows for the more loosely defined guard times 320and guard bands 330. This embodiment provides the MNOs with periodicmultiplexed access to a frequency bandwidth channel via both duty cycleand channel bandwidth that can be updated based on a current negotiatedresource allocation across networks.

In FIG. 13, a TDD-LTE real-time time-coordinated FDM signaling techniquewith non-shared eNodeB. In this embodiment, the spectrum split betweenM1 and M2 is real-time variable without matching for UL and DL. Thisgenerally means that coordinated scheduling is employed (e.g., via themaster scheduler 175 or via coordinated local schedulers 155). Aninter-MNO interface may be configured, in this regard, to coordinatewith the schedulers and create real time spectrum allocation.

Turning now to FIGS. 14-18, various exemplary FDD-LTE signalingtechniques are illustrated. In FIG. 14, an FDD-LTE TDM signalingtechnique is illustrated with Non-Shared eNodeB and a static scheduling.The guard times 320-1 in this embodiment are not necessarily equal tothe guard times 320-2. And, as this is a static schedulingconfiguration, channel time allocations are generally consistent foreach MNO. Frequency allocation is also static for the UL and DL

PDCCHs 301 are unique for each MNO and generated by each eNodeBindependently. RF parameters and cell size/layout may be different foreach MNO thereby leveraging existing user equipment and eNodeB withfewer changes. The user equipment, however, generally needs to handletwo distinct PDCCHs 301 on the same band.

In FIG. 15, an FDD-LTE TDM signaling technique with non-shared eNodeBand dynamic time allocation is illustrated. In this embodiment, theguard times 320-1 are again not necessarily equal to the guard times320-2. Scheduling is non-static meaning that channel time allocationsmay be variably sized for each MNO and that it may be external orhierarchical. However, frequency allocation is static for the UL and DL.PDCCHs 301 are unique for each MNO and are generated by each eNodeBindependently. RF parameters and cell size/layout may also differ foreach operator. User equipment generally needs to handle two distinctPDCCHS 301 on same band.

In FIG. 16, an FDD-LTE Dynamic FDM signaling technique with non-sharedeNodeB is illustrated. In this embodiment, a PDCCH 301 is sent forcenter frequency adjustment to dynamically allocate resources. A masterresource allocator (e.g., the master scheduler 175) may assign centerfrequencies to each MNO based on estimated traffic. Adjustment to centerfrequencies may be done through the PDCCH 301.

A control channel is maintained in the middle to provide agile resourceallocation. In this regard, the PDCCH 301 may require additional bits toassign the new center frequency. A 2-bit counter may be used to indicatea number of frames ahead in time when the new center frequencyadjustment is assigned. A “0” value in the counter indicates the currentcenter frequency. Alternatively, the MIB may be used to assign thecenter frequency.

Frequency allocation is dynamic for the UL and the DL. The PDCCHs 301are unique for each MNO and generated by each eNodeB independently.Again, the RF parameters and cell size/layout may be different for eachMNO. The arrow 340 indicates that there is no shift of the PSS and SSSsignals is needed if its current location remains within the MNOallocation. However, the arrow 341 indicates that adjustment ofresources may occur with the PDCCH 301 (e.g., a differential controlchannel frequency).

In FIG. 17, an FDD-LTE TDM semi-static time coordination with non-sharedeNodeB employing dynamic time allocation is illustrated. In thisembodiment, time coordination generally means that M1 and M2 changefrequency spectrum allocation in unison. The spectrum split between M1and M2 is semi-static, but there is no matching for the UL and the DL,similar to the embodiment illustrated in FIG. 16. This signalingtechnique does not require time coordination for changing spectrumallocation between the UL and the DL. However, an inter-MNO interfacemay be required for time coordination of frequency spectrum allocationbetween MNOs. Also, changes in spectrum allocation may cause a spectrumoverlap. Accordingly, guard times 320 and guard bands 330 may be used.

In FIG. 18, an FDD-LTE TDM real-time time coordination FDM signalingtechnique is illustrated with non-shared eNodeB. In this embodiment, aspectrum split/allocation between M1 and M2 is real-time variable, buthas no matching for the UL and the DL. Such may employ coordinatedscheduling (e.g., via the master scheduler 175 or via coordinated localschedulers 155), an inter-MNO interface, as well as an interface to anarbiter (e.g., the master scheduler 175).

Turning now to FIGS. 19-23, various exemplary shared eNodeB signalingtechniques are illustrated. In FIG. 19, a TDD-LTE TDM signalingtechnique with Shared eNodeB is illustrated.

In FIG. 20, a TDD-LTE semi-static time-coordinated FDM signalingtechnique with shared eNodeB and dual S1 with multiplexed PDCCH 301 isillustrated.

In FIG. 21, a TDD-LTE semi-static time-coordinated FDM signalingtechnique with shared eNodeB and dual S1 with dual PDCCH 301 isillustrated.

In FIG. 22, a TDD-LTE dynamic FDM signaling technique with shared eNodeBis illustrated. In this embodiment, one eNodeB is shared by “N” numberof MNOs. This signaling technique employs continuous OrthogonalFrequency Division Multiplexing (OFDM) without guard bands 330 on the DLand the UL. It also employs a common PDCCH 301 and each MNO resourceallocation is in real-time.

In FIG. 23, a TDD-LTE TDM signaling technique with shared eNodeB isillustrated. This embodiment employs dynamic time and frequencyallocation. Generally, resources are synchronized and dynamicallyallocated between MNOs. A guard time 320 is implemented for the DL andthe UL transitions (e.g., based on RTT of the user equipment). Also,there are generally two scheduling models. A first model includes acommon scheduler, such as the master scheduler 175, to coordinatesharing between MNOs for resource and user equipment allocation. Asecond model includes hierarchical scheduling where resources aredivided amongst MNOs via the master scheduler 175 on a shared eNodeB.The user equipment may perform scheduling on the UL within allocatedresources via “child schedulers” on the shared eNodeB.

The embodiments herein provide new cellular broadcast channels that canbe used to communicate spectrum use to cellular peers while providingcollision avoidance techniques to broadcast channels such that cellularpeers can dynamically enter and leave shared signaling. The cellularbroadcast channel leverages existing cellular broadcast channelsynchronization methods specific to the cellular air interface (e.g.,LTE). The broadcast channel indicates that it is a spectrum usebroadcast channel and includes a mobile network code and indicates thespectrum bands in use.

Each sequence of information pertaining to spectrum band in usegenerally indicates the spectrum band in use, the subcarriers in usewithin the band, and the time period of expected use for the subcarrierprior to release to another network. The cellular broadcast channel isgenerally used on a well-known narrow band frequency, such as WiFi. Thecellular network senses the frequency to ensure it is not being usedprior to broadcasting its spectrum use on that frequency. This avoidscollisions between cellular broadcast channels. Other networks can alsoscan the frequency to determine if the spectrum is in use.

The embodiments disclosed herein can also extend existing cellularbroadcast channels for cellular peers to communicate spectrum use toeach other. For example, as an alternative to the cellular broadcastchannel, the cellular network may use an extended cellular broadcastchannel to communicate its spectrum use. In this case, spectrum useinformation may be appended to the end of an existing broadcast channel.This broadcast channel indicates a spectrum use broadcast channel, amobile network code, and the spectrum bands that are in use. Similarly,each sequence of spectrum band in use information indicates the spectrumband in use, the subcarriers in use within the band, and the time periodof expected use for the subcarrier prior to release to another network.Another network may still need to scan the band to find the broadcastchannel as sense and collision avoidance techniques may not be used insuch an embodiment.

The embodiments disclosed herein also allow base stations 106 tobroadcast their spectrum use as WiFi traffic payloads or via MAC layersignaling. In this regard, each base station 106 would contain a WiFitransceiver for the sake of spectrum use communications. A WiFi SSID isthen broadcast to indicate spectrum use of the cellular network. TheSSID name may indicate it is being used for spectrum information.Alternatively, the 802.11 MAC layer broadcast messaging would indicate aspectrum information SSID. And, a WiFi device would be able to detectthe spectrum information SSID to “auto-associate”. Once associated, thebase station 106 broadcasts spectrum use information as an applicationor in the form of a MAC layer information response.

User equipment can also be configured to detect broadcast channels viacellular scanning and broadcast channel interpretation. The userequipment can also be configured to detect the broadcast channels over aWiFi traffic channel broadcasts (e.g., via cellular spectrum usebroadcast information as WiFi MAC signaling or traffic payloads). Theuser equipment can also be configured to detect broadcast channels overWiFi by extending the HS2.0 3GPP network information beacon. Forexample, 802.11u (part of 802.11-2012) includes a MAC layer informationexchange of 3GPP information. The MAC layer includes a mobile networkidentifier and an authentication mechanism identifier used in networkattachment. This information can be extended to include spectrum-in-useinformation.

Additionally, WiFi channel detection can be integrated into the basestations 106 so that a base station 106 can dynamically assignfrequencies. For example, an LTE base station can be configured todetect WiFi beacons that describe beacon use. In this regard, WiFi radiointerfaces can be integrated into the LTE base stations to operate as aWiFi device. The base station 106 would then scan and detect SSIDs tosee the spectrum is in use by WiFi. The SSIDs would indicate the bandsand channels in use by the WiFi network such that subscribers couldaccess them the other user equipment. A cellular network within avoidplacing cellular subcarriers in the spectrum when it is in use by theWiFi SSIDs. Alternatively, other unlicensed band receivers could beincorporated into the base station 106 to detect energy that may not beWiFi, including Zigbee, wireless microphones, and the like. From there,the base station 106 could dynamically assign frequencies to itssubscribers.

In one LTE embodiment, UE measurements related to inter-system (a.k.a.inter-RAT) mobility and/or Inter-frequency automatic neighbor relation(ANR) can be extended to dynamically include a WiFi cell as a neighbor.The ANR is a cellular technique where neighboring cells areautomatically discovered. Such an embodiment would support mobilityacross networks. For example, during WiFi network discovery, thecellular network can populate WiFi neighbor information in the ANR forthe sake of handover planning between WiFi and cellular. This is not aspectrum sharing topic, but rather a mobility technique that exploitsnetwork detection techniques that can also be used for spectrum sharing.

Wireless access points of WiFi networks can be configured to detect newcellular broadcast channels and/or extended cellular broadcast channelsand then apply 802.11 dynamic frequency selection (DSF) and channelselection principals to avoid collision with cellular use of thespectrum. Once the WiFi networks detect the spectrum in use by cellularnetworks, the WiFi networks can assign associated WiFi devices tochannels in the band that will not interfere with the cellular networkwhere they can assign channels to another band not in use by thecellular network. Enrollee stations (STAs) of Wi-Fi networks can also beconfigured to detect new cellular broadcast channels and/or extendedcellular broadcast channels to avoid cellular spectrums in use. Suchsolves interference issues with WiFi peer to peer transmissions.

Base stations 106 can also be configured to detect WiFi beacons andcontrol messages in order to avoid currently in use WiFi channels. Forexample, the base stations 106 can take into account the frequenciescurrently in use by cell network peers (e.g., different MCOs/MNOs) andWiFi end points as part of their traffic channel assignment decisions.For example, the base stations 106 can detect new broadcast channels orextended broadcast channels and then avoid using subcarriers or bandsindicated in the broadcast channels for transmission to devices on theirnetwork. This prevents interference between cellular networks.

Additionally, WiFi STAs and access points can take into account thefrequencies currently in use by cell network peers as part of their bandand traffic channel assignment decisions. For example, WiFi devices(e.g., user equipment) and access points can detect the spectrum in useby the cellular network via a broadcast SSID. WiFi access points thenavoid using the frequencies of cellular bands and subcarriers based onWiFi SSIDs and associated devices.

The embodiments disclosed herein provide many advantages over the priorart including dynamic coexistence of multiple cellular networks throughscheduled coordination and/or collision avoidance. For example, in someembodiments, a WiFi receiver is incorporated into a base station 106 forfrequency use detection as well as broadcasting to avoid signalingcollisions. Alternatively or additionally, an LTE receiver can beconfigured in your WiFi access point for frequency use detection andbroadcasting. Some embodiments also include dynamic mapping andinterleaving of LTE and WiFi carriers and subcarriers. Other embodimentsprovide for WiFi dissociation for spectrum reallocation to newfrequencies and/or the use of LTE forced network de-registrations forspectrum reallocation to new frequencies. And, the stations 106 can takeinto account the frequencies currently in use by cell network peers andWiFi end points as part of their traffic channel assignment decisions.WiFi STAs and access points can also take into account the frequenciescurrently in use by cell network peers as part of their band and trafficchannel assignment decisions.

The invention can take the form of an entirely hardware embodiment, anentirely software embodiment or an embodiment containing both hardwareand software elements. In one embodiment, the invention is implementedin software, which includes but is not limited to firmware, residentsoftware, microcode, etc. FIG. 24 illustrates a computing system 400 inwhich a computer readable medium 406 may provide instructions forperforming any of the methods disclosed herein.

Furthermore, the invention can take the form of a computer programproduct accessible from the computer readable medium 406 providingprogram code for use by or in connection with a computer or anyinstruction execution system. For the purposes of this description, thecomputer readable medium 406 can be any apparatus that can tangiblystore the program for use by or in connection with the instructionexecution system, apparatus, or device, including the computer system400.

The medium 406 can be any tangible electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system (or apparatus ordevice). Examples of a computer readable medium 406 include asemiconductor or solid state memory, magnetic tape, a removable computerdiskette, a random access memory (RAM), a read-only memory (ROM), arigid magnetic disk and an optical disk. Some examples of optical disksinclude compact disk-read only memory (CD-ROM), compact disk-read/write(CD-R/W) and DVD.

The computing system 400, suitable for storing and/or executing programcode, can include one or more processors 402 coupled directly orindirectly to memory 408 through a system bus 410. The memory 408 caninclude local memory employed during actual execution of the programcode, bulk storage, and cache memories which provide temporary storageof at least some program code in order to reduce the number of timescode is retrieved from bulk storage during execution. Input/output orI/O devices 404 (including but not limited to keyboards, displays,pointing devices, etc.) can be coupled to the system either directly orthrough intervening I/O controllers. Network adapters may also becoupled to the system to enable the computing system 400 to becomecoupled to other data processing systems, such as through host systemsinterfaces 412, or remote printers or storage devices throughintervening private or public networks. Modems, cable modem and Ethernetcards are just a few of the currently available types of networkadapters.

What is claimed is:
 1. A wireless telecommunications system, comprising:a plurality of wireless base stations, wherein each wireless basestation is operable to handle a session from a wireless device and tohandoff the session to another of the wireless base stations when thewireless device moves into a range of the other wireless base station;and a Mobile Central Office (MCO) communicatively coupled to each of thewireless base stations, wherein each of the wireless base stations iscommunicatively coupled to a remotely located master scheduling systemthrough the MCO, and wherein each of the wireless base stations isoperable to convey capacity information to the master scheduling system,and to acquire capacity from one or more wireless base stations ofanother MCO when directed by the master scheduling system.
 2. Thewireless telecommunications system of claim 1, wherein: a first of thewireless base stations is operable to complete use of the acquiredcapacity, and to relinquish the acquired capacity to the masterscheduling system.
 3. The wireless telecommunications of claim 1,wherein: a first of the wireless base stations is operable tocommunicate with the wireless device via Long Term Evolution (LTE)wireless signaling.
 4. The wireless telecommunications of claim 1,wherein: a first wireless base station is operable to communicate withthe wireless device via WiFi signaling at WiFi frequencies.
 5. Thewireless telecommunications of claim 1, wherein: a first wireless basestation is operable to communicate with the wireless device via thecapacity acquired from the other MCO when directed by the masterscheduling system.
 6. The wireless telecommunications of claim 1,wherein: a first wireless base station is operable to direct thewireless device to communicate through the other MCO via the capacityacquired from the other MCO when directed by the master schedulingsystem.
 7. The wireless telecommunications of claim 1, wherein: theacquired capacity includes a block of frequency bandwidth.
 8. Thewireless telecommunications system of claim 7, wherein: the MCO isoperable to control a Time Division Multiple Access signal, a FrequencyDivision Multiple Access signal, a Code Division Multiple Access signal,an Orthogonal Frequency Division Multiple Access signal, or acombination thereof in the block of frequency bandwidth.
 9. A methodoperable with a wireless telecommunications system comprising aplurality of wireless base stations and a Mobile Central Office (MCO),wherein each wireless base station is operable to handle a session froma wireless device and to handoff the session via the MCO to another ofthe wireless base stations when the wireless device moves into a rangeof the other wireless base station, the method comprising: establishinga link from a first of the wireless base stations to a remotely locatedmaster scheduling system through the MCO; conveying capacity informationfrom the first wireless base station to the master scheduling systemthrough the established link; and via the first wireless base station,acquiring capacity from one or more wireless base stations of anotherMCO when directed by the master scheduling system.
 10. The method ofclaim 9, further comprising: via the first wireless base station,completing use of the acquired capacity; and relinquishing the acquiredcapacity to the master scheduling system.
 11. The method of claim 9,further comprising: via the first wireless base station, communicatingwith the wireless device via Long Term Evolution (LTE) wirelesssignaling.
 12. The method of claim 9, further comprising: via the firstwireless base station, communicating with the wireless device via WiFisignaling at WiFi frequencies.
 13. The method of claim 9, furthercomprising: via the first wireless base station, communicating with thewireless device via the capacity acquired from the other MCO.
 14. Themethod of claim 9, further comprising: via the first wireless basestation, directing the wireless device to communicate through the otherMCO via the capacity acquired from the other MCO.
 15. The method ofclaim 9, wherein: the acquired capacity includes a block of frequencybandwidth; and the method further comprises: via the MCO, controlling aTime Division Multiple Access signal, a Frequency Division MultipleAccess signal, a Code Division Multiple Access signal, an OrthogonalFrequency Division Multiple Access signal, or a combination thereof inthe block of frequency bandwidth.
 16. A master scheduling system,comprising: an interface communicatively coupled to a plurality ofMobile Central Offices (MCOs), wherein each MCO is communicativelycoupled to a plurality of wireless base stations, and wherein eachwireless base station is operable to handle a session from a wirelessdevice; and a processor communicatively coupled to the interface andoperable to detect capacity on at least a portion of the wireless basestations, to determine that a first wireless base station of a first ofthe MCOs needs additional capacity, to request capacity from at leastone wireless base station of a second of the MCOs, and to direct thefirst wireless base station of the first MCO to acquire the requestedcapacity.
 17. The master scheduling system of claim 16, wherein: theprocessor is further operable to determine that the first wireless basestation of the first MCO has completed use of the acquired capacity, andto direct said at least one wireless base station of the second MCO toreacquire the capacity.
 18. The master scheduling system of claim 16,wherein: the acquired capacity includes a block of frequency bandwidth;and the first MCO is operable to control a Time Division Multiple Accesssignal, a Frequency Division Multiple Access signal, a Code DivisionMultiple Access signal, an Orthogonal Frequency Division Multiple Accesssignal, or a combination thereof in the block of frequency bandwidth.